home *** CD-ROM | disk | FTP | other *** search
/ InfoMagic Internet Tools 1995 April / Internet Tools.iso / infoserv / www / cern / dev / www-talk.9301-9306.Z / www-talk.9301-9306 / text1399.txt < prev    next >
Encoding:
Text File  |  1995-04-24  |  2.7 KB  |  64 lines
  1.     I am currently writing the hypertext doc to a class library
  2. which I want to be fully transparent for the public. Thus, I
  3. prepared an image of the Class Inheritance Tree with neat
  4. boxes. I thought I'd use the ISMAP feature [I have XMosaic v1.1
  5. for SGI-Irix4d]: I followed your demo, i.e. I have a file which
  6. contains
  7.                                                         <xmp>
  8. <A HREF="./decodeMGLIB"><IMG SRC="MGLIB-all.gif" ISMAP>
  9. </A>
  10.                                                         </xmp>
  11. and in the same dir a file
  12.                                                         <xmp>
  13. /decodeMGLIB
  14.                                                         </xmp>
  15. containing
  16.                                                         <xmp>
  17. <A HREF="/decodeMGLIB?90,400">ISU</A>
  18. <A HREF="/decodeMGLIB?180,299">MultiGrid</A>
  19.                                                         </xmp>
  20. Now, only if I accidentally hit the right coordinates,
  21. (90,400) or (180,299), I get the wanted answer, written to files
  22. named
  23.                                                         <xmp>
  24. /decodeMGLIB?90,400
  25. /decodeMGLIB?180,299
  26.                                                         </xmp>
  27.  
  28. respectively, while for other coordinates, I get the error:
  29.                                                         <XMP>
  30. **** HTAccess: socket or file number returned by obsolete
  31. load routine!  **** HTAccess: Internal software error.
  32. Please mail www-bug@info.cern.ch!
  33.                                                         </XMP>
  34. In his reply, Tony Sanders (sanders@bsdi.com)
  35. who contributed this feature said he did not even know the
  36. CERN httpd supported it. Tony also writes:
  37.                                                         <PRE>
  38.   What Mosaic
  39.   should be passing to the server for your example
  40.   would be:
  41.  
  42.   GET /decode?xxx,yyy
  43.  
  44.   It's the job of the server to decode the xxx,yyy
  45.   coords and translate that to some document.
  46.  
  47.   > these are the upper right corners of subimages
  48.  
  49.   I would imagine that you have to describe both corners,
  50.   and I'll bet it's the upper-left and lower-right, not
  51.   upper-right but that's just a guess.
  52.                                                         </PRE>
  53. Now, I dont know whether this quote helps, but maybe one or the
  54. other wizard at CERN, or an XMosaic expert knows the answer.
  55.   If that should be necessary: the files I am talking about above are
  56. at at URL http://info.desy.de:80/pub/www/refs/test, or
  57. <A HREF="http://info.desy.de:80/pub/www/refs/test">here</a>
  58. (if you're reading this with WWW)
  59.                                                                 <P>
  60.         <A HREF="http://info.desy.de:80/pub/www/people/marcus.html">
  61. marcus                                                  </a>
  62.  
  63.  
  64.